System and method for providing time zone as instant messaging presence

ABSTRACT

A system and method are provided to obtain and use time zone information as presence in instant messaging. The time zone information is obtained by a user&#39;s mobile device and is sent to other mobile devices corresponding to the user&#39;s contacts. The time zone information of a contact may be displayed on the user&#39;s IM application, including the contact list and instant messaging conversation window. The location of the mobile device may also be provided. The user uses the time zone and location information to discern the status of a contact. Rule-based decisions that rely on the time zone information are also used to affect the operation of the instant messaging application.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/713,923 filed on Feb. 26, 2010 which claims priority from U.S.Provisional Application No. 61/249,444 filed on Oct. 7, 2009, bothincorporated herein by reference.

TECHNICAL FIELD

The following relates to systems and methods for providing time zoneinformation as instant messaging presence.

BACKGROUND

Instant messaging has become a popular way of electronicallycommunicating in a conversational style, in particular using a mobile orhandheld device. Whether instant messaging on a desktop computer or amobile device, profiles or presence information are often used to allowa user to view the current status of other contacts, as well as allowother contacts to view the current status of the user. For example, thepresence information may show a contact is busy or available.

When instant messaging with contacts or “buddies”, a user and a contactmay be in different situations. For example, if the user is aware that acontact is busy, then the user may decide not to send a message to thecontact. However, displaying whether a contact is busy or available maynot provide the user with sufficient presence information to discern thesituation of the contact.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will now be described by way of example only with referenceto the appended drawings wherein:

FIG. 1 is a schematic diagram illustrating a system in which data itemsare pushed from a host system to a mobile device.

FIG. 2 is a block diagram of an example embodiment of a mobile device.

FIG. 3 is a block diagram illustrating example ones of the othersoftware applications and components shown in FIG. 2.

FIG. 4 is a system diagram showing one configuration for instantmessaging on multiple platforms.

FIG. 5 is a system diagram showing one configuration for retrieving andsharing time zone information through instant messaging.

FIG. 6 is an example screen shot of an instant messaging profile forUser A.

FIG. 7 is a flow chart illustrating example computer executableinstructions for allowing whether time zone information, or time zoneand location information is allowed to be shared with other mobiledevices.

FIG. 8 is an example screen shot of an instant messaging contact list asseen by User A and showing the time zone information as presence for thecontacts.

FIG. 9 is an example screen shot of User B's contact profile as seen byUser A.

FIG. 10 is a flow chart illustrating example computer executableinstructions between mobile device A and mobile device B for retrievingtime zone information, or time zone and location information, frommobile device B.

FIG. 11 is a pictorial diagram of a mobile device displaying a screenshot of an instant messaging conversation between User A and User B, asseen by User A, and displaying when User B's message was received.

FIG. 12 is a pictorial diagram of a mobile device displaying a screenshot of an instant messaging conversation between User A and User B, asseen by User A, and displaying when User A's message was sent.

FIG. 13 is a pictorial diagram of a mobile device displaying a screenshot of an instant messaging conversation between User A and User B, asseen by User A, and displaying the local time and location of User Bwith respect to User A's sent message.

FIG. 14 is a flow chart illustrating example computer executableinstructions for displaying a contact's local time or, local time andlocation, with respect to sent and received messages.

FIG. 15 is a flow chart illustrating example computer executableinstructions for retrieving time zone information, or time zone andlocation information, from a received instant message.

FIGS. 16, 17 and 18 are pictorial diagrams of a mobile device displayingan instant messaging conversation between User A and User B, and showinga prompt that confirms whether a new message from User A should be sentto User B, based on User B's local time.

FIG. 19 is a flow chart illustrating example computer executableinstructions for displaying a prompt to confirm whether a new messageshould be sent based on the contact's local time.

FIG. 20 is an example screen shot of an instant messaging contact listas seen by User A and showing relative time differences between each ofthe contacts and User A.

FIG. 21 is a pictorial diagram of a mobile device displaying an instantmessaging conversation between User A and User B, as well as showing anew incoming message from User F with User F's local time.

FIG. 22 is an example screen shot of a date or time, or both,application.

FIG. 23 is an example screen shot of an instant messaging contact listas seen by User A and showing notifications of changes in time zone ofthe contacts.

FIG. 24 is an example screen shot of an instant messaging contact listas seen by User A and showing a notification that a contact has changedtime zones.

FIG. 25 is a flow chart illustrating example computer executableinstructions for displaying a notification that a contact has changedtime zones.

FIG. 26 is an example screen shot of an instant messaging profile forUser A and showing an option to enable the display of User A's roamingstatus.

FIG. 27 is an example screen shot of an instant messaging contact listas seen by User A and showing a notification a contact's time zonestatus and roaming status.

FIG. 28 is a flow chart illustrating example computer executableinstructions for broadcasting and retrieving time zones as instantmessaging presence.

FIG. 29 is an example screen shot of an instant messaging contact listas seen by User A and showing a map of the different time zones.

FIG. 30 is a flow chart illustrating example computer executableinstructions for providing time zone information as instant messagingpresence.

FIG. 31 is a flow chart illustrating example computer executableinstructions for displaying time zone information for at least onecontact listed in an instant messaging application.

DETAILED DESCRIPTION OF THE DRAWINGS

In instant messaging (IM) applications the presence of a user, or auser's contact, or both may change depending on various circumstances. Auser and a contact may be in different circumstances, and thus, it isdesirable to convey such circumstances. It has been realized that when auser and a contact are in different time zones, the difference in timezones may affect whether instant messages are sent, as well as affectthe expectation as to when a sent instant message is read by thecontact.

In the following, a method and system are provided to identify the localtime zone of a mobile device, and allow a user to share the time zoneinformation with contacts through an instant messaging application.Similarly, the user would be able to view the local time zoneinformation of the instant messaging contacts. The time zone informationcan be exchanged between instant messaging users through the instantmessaging application's presence data. It will be appreciated thatalthough the following examples are provided in the context of instantmessaging, the principles discussed herein are equally applicable toother conversational-type message exchange services, e.g. SMS, MMS, etc.

The following examples include communications between mobile or handhelddevices, which will be commonly referred to as mobile deviceshereinafter and referred to by numeral 10.

The mobile device 10 can be a two-way communication device with advanceddata communication capabilities including the capability to communicatewith other mobile devices 10 or computer systems through a network oftransceiver stations. The mobile device 10 may also have the capabilityto allow voice communication. Depending on the functionality provided bythe mobile device 10, it may be referred to as a data messaging device,a two-way pager, a cellular telephone with data messaging capabilities,a wireless Internet appliance, or a data communication device (with orwithout telephony capabilities). The mobile device 10 can also be onethat is used in a system that is configured for continuously routing allforms of pushed information from a host system 25 to the mobile device10. One example of such a system will now be described making referenceto FIG. 1.

FIG. 1 is an example system diagram showing the redirection of user dataitems (such as message A or C) from a corporate enterprise computersystem (host system) 25 to the user's mobile device 10 via a wirelessrouter 26. The wireless router 26 provides the wireless connectivityfunctionality as it acts to both abstract most of the wireless network's20 complexities, and it also implements features necessary to supportpushing data to the mobile device 10. Although not shown, a plurality ofmobile devices may access data from the host system 25. In this example,message A in FIG. 1 represents an internal message sent from, e.g. adesktop computer (not shown) within the host system 25, to any number ofserver computers in the corporate network (e.g. LAN), which may, ingeneral, include a database server, a calendar server, an E-mail serveror a voice-mail server.

Message C in FIG. 1 represents an external message from a sender that isnot directly connected to the host system 25, such as the user's mobiledevice 10, some other user's mobile device (not shown), or any userconnected to the public or private network 24 (e.g. the Internet).Message C could be e-mail, voice-mail, calendar information, databaseupdates, web-page updates or could even represent a command message fromthe user's mobile device 10 to the host system 25. The host system 25may comprise, along with the typical communication links, hardware andsoftware associated with a corporate enterprise computer network system,one or more wireless mobility agents, a TCP/IP connection, a collectionof data stores, (for example a data store for e-mail could be anoff-the-shelf mail server like Microsoft Exchange® Server or LotusNotes® Server), all within and behind a corporate firewall.

The mobile device 10 may be adapted for communication within wirelessnetwork 20 via wireless links, as required by each wireless network 20being used. As an illustrative example of the operation for a wirelessrouter 26 shown in FIG. 1, consider a data item A, repackaged in outerenvelope B (the packaged data item A now referred to as “data item (A)”)and sent to the mobile device 10 from an Application Service Provider(ASP) in the host system 25. Within the ASP is a computer program,similar to a wireless mobility agent, running on any computer in theASP's environment that is sending requested data items from a data storeto a mobile device 10. The mobile-destined data item (A) is routedthrough the network 24, and through the wireless router's 26 firewallprotecting the wireless router 26 (not shown).

Although the above describes the host system 25 as being used within acorporate enterprise network environment, this is just one embodiment ofone type of host service that offers push-based messages for a handheldwireless device that is capable of notifying and presenting the data tothe user in real-time at the mobile device when data arrives at the hostsystem.

By offering a wireless router 26 (sometimes referred to as a “relay”,“message server”, “data redirector”, etc.), there are a number of majoradvantages to both the host system 25 and the wireless network 20. Thehost system 25 in general runs a host service that is considered to beany computer program that is running on one or more computer systems.The host service is said to be running on a host system 25, and one hostsystem 25 can support any number of host services. A host service may ormay not be aware of the fact that information is being channelled tomobile devices 10. For example an e-mail or message program 138 (seeFIG. 2) might be receiving and processing e-mail while an associatedprogram (e.g. an e-mail wireless mobility agent) is also monitoring themailbox for the user and forwarding or pushing the same e-mail to awireless device 10. A host service might also be modified to preparedand exchange information with mobile devices 10 via the wireless router26, like customer relationship management software. In a third example,there might be a common access to a range of host services. For examplea mobility agent might offer a Wireless Access Protocol (WAP) connectionto several databases.

Although the system is exemplified as operating in a two-waycommunications mode, certain aspects of the system could be used in a“one and one-half” or acknowledgment paging environment, or even with aone-way paging system. In such limited data messaging environments, thewireless router 26 still could abstract the mobile device 10 andwireless network 20, offer push services to standard web-based serversystems and allow a host service in a host system 25 to reach the mobiledevice 10 in many countries.

The host system 25 shown herein can have many methods when establishinga communication link to the wireless router 26. For one skilled in theart of data communications the host system 25 could use connectionprotocols like TCP/IP, X.25, Frame Relay, ISDN, ATM or many otherprotocols to establish a point-to-point connection. Over this connectionthere are several tunnelling methods available to package and send thedata, some of these include: HTTP/HTML, HTTP/XML, HTTP/Proprietary, FTP,SMTP or some other proprietary data exchange protocol. The type of hostsystems 25 that might employ the wireless router 26 to perform pushcould include: field service applications, e-mail services, stock quoteservices, banking services, stock trading services, field salesapplications, advertising messages and many others. This wirelessnetwork 20 abstraction is made possible by the wireless router 26, whichimplements this routing and push functionality. The type ofuser-selected data items being exchanged by the host could include:E-mail messages, calendar events, meeting notifications, addressentries, journal entries, personal alerts, alarms, warnings, stockquotes, news bulletins, bank account transactions, field serviceupdates, stock trades, heart-monitoring information, vending machinestock levels, meter reading data, GPS data, etc., but could,alternatively, include any other type of message that is transmitted tothe host system 25, or that the host system 25 acquires through the useof intelligent agents, such as data that is received after the hostsystem 25 initiates a search of a database or a website or a bulletinboard.

The wireless router 26 provides a range of services to make creating apush-based host service possible. These networks may comprise: (1) theCode Division Multiple Access (CDMA) network, (2) the Groupe SpecialMobile or the Global System for Mobile Communications (GSM) and theGeneral Packet Radio Service (GPRS), and (3) the existing and upcomingthird-generation (3G) and fourth generation (4G) networks like EDGE,UMTS and HSDPA, LTE, Wi-Max etc. Some older examples of data-centricnetworks include, but are not limited to: (1) the Mobitex Radio Network(“Mobitex”) and (2) the DataTAC Radio Network (“DataTAC”).

To be effective in providing push services for host systems 25, thewireless router 26 may implement a set of defined functions. It can beappreciated that one could select many different hardware configurationsfor the wireless router 26, however, many of the same or similar set offeatures would likely be present in the different configurations.

An example configuration for the mobile device 10 is illustrated inFIGS. 2-3. Referring first to FIG. 2, shown therein is a block diagramof an example embodiment of a mobile device 10. The mobile device 10comprises a number of components such as a main processor 102 thatcontrols the overall operation of the mobile device 10. Communicationfunctions, including data and voice communications, are performedthrough a communication subsystem 104. The communication subsystem 104receives messages from and sends messages to a wireless network 20. Inthis example embodiment of the mobile device 10, the communicationsubsystem 104 is configured in accordance with the GSM and GPRSstandards, which are used worldwide. Other communication configurationsthat are equally applicable are the 3G and 4G networks discussed above.New standards are still being defined, but it is believed that they willhave similarities to the network behaviour described herein, and it willalso be understood by persons skilled in the art that the embodimentsdescribed herein are intended to use any other suitable standards thatare developed in the future. The wireless link connecting thecommunication subsystem 104 with the wireless network 20 represents oneor more different Radio Frequency (RF) channels, operating according todefined protocols specified for GSM/GPRS communications.

The main processor 102 also interacts with additional subsystems such asa Random Access Memory (RAM) 106, a flash memory 108, a display 110, anauxiliary input/output (I/O) subsystem 112, a data port 114, a keyboard116, a speaker 118, a microphone 120, a GPS receiver 121, short-rangecommunications 122, and other device subsystems 124. As will bediscussed below, the short-range communications 122 can implement anysuitable or desirable device-to-device or peer-to-peer communicationsprotocol capable of communicating at a relatively short range, e.g.directly from one device to another. Examples include Bluetooth®, ad-hocWiFi, infrared, or any “long-range” protocol re-configured to utilizeavailable short-range components. It will therefore be appreciated thatshort-range communications 122 may represent any hardware, software orcombination of both that enable a communication protocol to beimplemented between devices or entities in a short range scenario, suchprotocol being standard or proprietary.

Some of the subsystems of the mobile device 10 performcommunication-related functions, whereas other subsystems may provide“resident” or on-device functions. By way of example, the display 110and the keyboard 116 may be used for both communication-relatedfunctions, such as entering a text message for transmission over thenetwork 20, and device-resident functions such as a calculator or tasklist.

The mobile device 10 can send and receive communication signals over thewireless network 20 after required network registration or activationprocedures have been completed. Network access is associated with asubscriber or user of the mobile device 10. To identify a subscriber,the mobile device 10 may use a subscriber module component or “smartcard” 126, such as a Subscriber Identity Module (SIM), a Removable UserIdentity Module (RUIM) and a Universal Subscriber Identity Module(USIM). In the example shown, a SIM/RUIM/USIM 126 is to be inserted intoa SIM/RUIM/USIM interface 128 in order to communicate with a network.Without the component 126, the mobile device 10 is not fully operationalfor communication with the wireless network 20. Once the SIM/RUIM/USIM126 is inserted into the SIM/RUIM/USIM interface 128, it is coupled tothe main processor 102.

The mobile device 10 is typically a battery-powered device and in thisexample includes a battery interface 132 for receiving one or morerechargeable batteries 130. In at least some embodiments, the battery130 can be a smart battery with an embedded microprocessor. The batteryinterface 132 is coupled to a regulator (not shown), which assists thebattery 130 in providing power V+ to the mobile device 10. Althoughcurrent technology makes use of a battery, future technologies such asmicro fuel cells may provide the power to the mobile device 10.

The mobile device 10 also includes an operating system 134 and softwarecomponents 136 to 146 which are described in more detail below. Theoperating system 134 and the software components 136 to 146 that areexecuted by the main processor 102 are typically stored in a persistentstore such as the flash memory 108, which may alternatively be aread-only memory (ROM) or similar storage element (not shown). Thoseskilled in the art will appreciate that portions of the operating system134 and the software components 136 to 146, such as specific deviceapplications, or parts thereof, may be temporarily loaded into avolatile store such as the RAM 106. Other software components can alsobe included, as is well known to those skilled in the art.

The subset of software applications 136 that control basic deviceoperations, including data and voice communication applications, may beinstalled on the mobile device 10 during its manufacture. Softwareapplications may include a message application 138, a device statemodule 140, a Personal Information Manager (PIM) 142, a connect module144 and an IT policy module 146. A message application 138 can be anysuitable software program that allows a user of the mobile device 10 tosend and receive electronic messages, wherein messages are typicallystored in the flash memory 108 of the mobile device 10. A device statemodule 140 provides persistence, i.e. the device state module 140ensures that important device data is stored in persistent memory, suchas the flash memory 108, so that the data is not lost when the mobiledevice 10 is turned off or loses power. A PIM 142 includes functionalityfor organizing and managing data items of interest to the user, such as,but not limited to, e-mail, text messages, instant messages, contacts,calendar events, and voice mails, and may interact with the wirelessnetwork 20. A connect module 144 implements the communication protocolsthat are required for the mobile device 10 to communicate with thewireless infrastructure and any host system 25, such as an enterprisesystem, that the mobile device 10 is authorized to interface with. An ITpolicy module 146 receives IT policy data that encodes the IT policy,and may be responsible for organizing and securing rules such as the“Set Maximum Password Attempts” IT policy.

Other types of software applications or components 139 can also beinstalled on the mobile device 10. These software applications 139 canbe pre-installed applications (i.e. other than message application 138)or third party applications, which are added after the manufacture ofthe mobile device 10. Examples of third party applications includegames, calculators, utilities, etc. The additional applications 139 canbe loaded onto the mobile device 10 through at least one of the wirelessnetwork 20, the auxiliary I/O subsystem 112, the data port 114, theshort-range communications subsystem 122, or any other suitable devicesubsystem 124.

The data port 114 can be any suitable port that enables datacommunication between the mobile device 10 and another computing device.The data port 114 can be a serial or a parallel port. In some instances,the data port 114 can be a USB port that includes data lines for datatransfer and a supply line that can provide a charging current to chargethe battery 130 of the mobile device 10.

For voice communications, received signals are output to the speaker118, and signals for transmission are generated by the microphone 120.Although voice or audio signal output is accomplished primarily throughthe speaker 118, the display 110 can also be used to provide additionalinformation such as the identity of a calling party, duration of a voicecall, or other voice call related information.

The main processor 102 can also control a backlight 36 for conservingbattery life when the mobile device 10 is locked or otherwise not in use(e.g. in a holster). The backlight 36 can be used to illuminate thedisplay 110 when the mobile device 10 is being used. The backlight 36can be associated with an idle timer 34 such that an idle time can betracked and if it reaches or exceeds a certain predetermined threshold(or user definable threshold), the backlight 36 is turned off. As willbe explained below, the idle timer 34 can also be used to provide acurrent idle time to the main processor 102 for other uses such as todetermine inactivity of the user. The main processor 102 may alsoutilize data provided by an orientation sensor 35. The orientationsensor 35 may comprise an inclinometer or other sensor capable ofdetermining the orientation of the mobile device 10 with respect to adatum.

For composing data items, such as e-mail messages, for example, a useror subscriber could use a touch-sensitive overlay (not shown) on thedisplay 110 that is part of a touch screen display (not shown), inaddition to possibly the auxiliary I/O subsystem 112. The auxiliary I/Osubsystem 112 may include devices such as: a mouse, track ball, infraredfingerprint detector, or a roller wheel with dynamic button pressingcapability. A composed item may be transmitted over the wireless network20 through the communication subsystem 104.

FIG. 3 shows an example of the other software applications andcomponents 139 that may be stored on and used with the mobile device 10.Only examples are shown in FIG. 3 and such examples are not to beconsidered exhaustive. In this example, a host instant messageapplication 50, 3^(rd) party instant messaging application 52, phoneapplication 54, address book 56 and a profiles application 58 are shownto illustrate the various features that may be provided by the mobiledevice 10. Also shown in FIG. 3 is the message application 138, which inthe following will be referred to as an email application 138 forclarity and stores or otherwise has access to a message database 36 forstoring incoming and outgoing messages as well as those stored invarious folders. It will be appreciated that the various applicationsmay operate independently or may utilize features of other applications.For example, the phone application 54 and email application 138 may usethe address book 56 for contact details obtained from a list of contacts34.

The host system instant messaging application 50 is an instant messagingservice that is hosted and provided by the host system 25 in thisexample, e.g. using a messaging server at the wireless router 26 asexemplified in FIG. 4 and discussed below. The host system instantmessaging application 50 includes or otherwise has access to a hostbuddy list 30 for storing contact information for buddies also using thehost system instant messaging application 50. The 3^(rd) part instantmessaging application 52 includes or otherwise has access to a 3^(rd)party buddy list 32 for storing contact information for buddies alsousing the 3^(rd) party instant messaging application 52. It will beappreciated that any number of host system or 3^(rd) party instantmessaging services can be installed and run on the mobile device 10 andthus the two shown in FIG. 3 are for illustrative purposes only. Also,it will be appreciated that in other embodiments, only a single instantmessaging service may be supported or a unified instant messagingservice that combines contact or buddy lists for multiple instantmessaging services and utilizes a common user interface (not shown).

FIG. 4 illustrates a configuration suitable for a user of mobile deviceA, hereafter referred to as mobile device 10A, to conduct instantmessaging with buddies included in their IM buddy lists 30, 32. It canbe seen in FIG. 4 that the two examples of instant messaging systemsfrom FIG. 3 are shown. The host system IM service is shown that utilizesthe wireless router 26 and a 3rd party instant messaging service is alsoshown that utilizes a 3rd party instant messaging server 86 accessed bymobile device 10A through the network 20. The host system IM service canbe implemented in any suitable manner but for the sake of illustration,the following describes the host system IM service as being a personalidentification number (PIN)-based messaging system. As can be seen, the3rd party instant messaging server 86 may also communicate with users ofa desktop 85 thus facilitating instant messaging between users of adesktop 85 and between a mobile device user 10 and a user on desktop 85.Similarly, the PIN-based messaging system may also facilitatecommunications with desktop users 85.

In the embodiment illustrated in FIG. 4, the PIN-based messaging systemis implemented using a server-based communication infrastructure, suchas one that provides email, SMS, voice, Internet and othercommunications. Particularly suitable for hosting a peer-to-peermessaging server 80, is the wireless router 26 used in systems such asthose shown in FIG. 1. In FIG. 4, the wireless router 26 facilitatescommunications such as instant messaging between mobile device 10A andmobile devices for User B, User C and User D, denoted by 10B, 10C and10D respectively. It will be appreciated that the number of usersparticipating in the example shown in FIG. 4 is for illustrativepurposes only. Instant messaging is provided by the instant messagingapplications 50, 52 stored on each mobile device 10A-10D which can beinitiated, for example, by highlighting and selecting a correspondinginstant messaging icon from a display for the mobile device 10. In thehost system IM service, the wireless router 26 routes messages betweenthe mobile devices 10A-10D according to a PIN-to-PIN protocol 82.

A PIN-to-PIN based instant message is generally denoted by numeral 68 inFIG. 4 and may differ in structure from a 3^(rd) party based instantmessage 84. In a PIN-based messaging protocol 82, each message 68 hasassociated therewith a PIN corresponding to the mobile device 10 whichhas sent the message 68 (source) and includes a destination PINidentifying the intended recipient (destination). Although not shown inFIG. 4, each message 68 generally comprises a body, which contains thecontent for the message 68 (e.g. text), and a header, which containsvarious fields used for transmitting and processing each message 68. Inthis example, the header includes a message type field to specify thetype of transmission (e.g. PIN, SMS etc.), a source field to specify thedevice address for the sender, a destination field to specify the deviceaddress for the intended recipient, a conversation ID field to identifywhich conversation thread the message 68 corresponds to (e.g. such thateach message 68 is identified by the conversation in which it was sent),and a timestamp field to indicate the time (and if desired, the date) atwhich the message 68 was sent by the designated sender.

Although not shown in FIG. 4, one or more tags can also be used toindicate to the host system IM application 50, upon receipt of a message68, that the message 68 has certain attributes such as a subject that isto be displayed, whether additional information is being transported(i.e. data or information in addition to the message content), orwhether the message 68 is being used for some other purpose such asprovisioning, synchronization, etc. In general, in a PIN based messagingprotocol 82, the sender of the message 68 knows the PIN of the intendedrecipient. This is preferably established when the two devices requestto add each other to their respective contact or buddy lists. At thetime of requesting new contacts, in traditional PIN-to-PIN protocols 82,the two respective PIN numbers may be exchanged via request e-mailswhich are configured to be intercepted by the respective host systeminstant messaging applications 50 so as to not appear in the messagelist or “inbox” of the user.

It can be seen in the example shown in FIG. 4 that mobile device 10A cancommunicate directly with any of the mobile devices 10B-10D through thepeer-to-peer messaging server 80 as indicated by the short-dashed line.Instant messaging can also be accomplished through the 3rd party IMserver 86 by sending 3rd party based instant messages 84 over thewireless network 20 as indicated by the long-dashed line.

When conducting a PIN-to-PIN instant messaging session according to theembodiment shown in FIG. 4, the mobile devices 10A-10D can communicatedirectly with the wireless router 26 in a client based exchange where,similar to other peer-to-peer programs, an intermediate server is notrequired. A message 68 sent by one mobile device 10 is received by thewireless router 26, which obtains the PIN number for the intendedrecipient from information associated with the message (e.g. a data log)or from the message itself. Upon obtaining the recipient's PIN accordingto the PIN-to-PIN protocol 82, the wireless router 26 then routes themessage 68 to the recipient associated with the mobile device 10 havingsuch PIN. The wireless router 26 typically also provides a deliveryconfirmation to the original sender, which may or may not be displayedto the user. The destination device can also provide such deliveryinformation. The wireless router 26 should be capable of routingmessages 68 reliably and hold onto the messages 68 until they aresuccessfully delivered. Alternatively, if delivery cannot be made aftera certain timeout period, the wireless router 26 may provide a responseindicating a failed delivery. The wireless router 26 may choose toexpire a message 68 if a certain waiting period lapses.

It will also be appreciated that, as noted above, instant messaging canbe implemented using any other suitable protocol such as SMS. In SMS, amessage is transmitted to an SMS center (SMSC) within a carrier'sinfrastructure, and then delivered to the mobile phone number of thedestination device. The SMSC would also be configured to hold ontomessages and deliver then once the destination device is withincoverage.

When conducting an instant messaging session using a 3rd party IMapplication, access to the 3rd party IM server 86 is first establishedand instant messages 84 exchanged over the wireless network 20 accordingto the appropriate protocol used by the 3rd party. It will beappreciated that the principles discussed below are equally applicableto both PIN-to-PIN messaging and other Internet service-based instantmessaging systems hosted by such 3rd parties.

Turning now to FIG. 5, an embodiment of a system configured forobtaining and sharing time zone information between mobile device 10Aand mobile device 10B is shown. A mobile device 10, for example mobiledevice 10A, is able to retrieve time zone information from varioussources. In one embodiment a time zone application 210, either separatefrom or part of the IM application 50, retrieves time zone informationthrough the communication subsystem 104. For example, as mobile device10A moves from one location to another, a cellular carrier or networkcarrier 216 tracks the location of mobile device 10A and accordinglytransmits the local time, as well as time zone information, to mobiledevice 10A. The carrier 216 may provide the time zone information in oneof the frames that the carrier 216 broadcasts, which, in some cases, issimilar to providing network time. Thus, the carrier 216 determines andtransmits the time zone information to mobile device 10A through thecommunication subsystem 104. The time zone information may also bedetermined by the location of mobile device 10A relative to various celltowers 218. In other words, the communication subsystem 104 is aware ofthe location of one or more of the cell towers 218 with which it iscommunicating and, thus, based on the location of the cell towers 218,the location and time zone information of mobile device 10A isdetermined. It can be appreciated that the time zone information may besent to a mobile device 10 in response to any one of the followingevents: 1) upon registering on the network; 2) when the mobile device 10geographically relocates to a different local time zone; 3) when thenetwork changes its local time zone, e.g. between summer and wintertime; 4) when the network changes its identity; and 5) at any timeduring a signalling connection with mobile station.

The time zone information may also be determined using the GPS receiver121, which is in communication with one or more GPS satellites 220. Forexample, the location of mobile phone 10A may be determined through theGPS receiver 121, thereby allowing the time zone information to be alsodetermined.

The time zone information may also be determined through user input 214.The user may directly input or select the time zone for which the userwishes to display. Alternatively, the user may input or select alocation (e.g. city) from which the time zone can be determined.

It can thus be seen that there are a number of ways in which the timezone module 210 can obtain the time zone information, and that any othersystems and methods for obtaining time zone information are applicableto the principles described herein.

The IM application 50 on mobile device 10A may share the time zoneinformation, or both the time zone and location information, with one ormore mobile devices, for example mobile device 10B. In one embodiment,the time zone information is shared in the same way that presenceinformation is shared. As discussed above, mobile device 10A and mobiledevice 10B may be in direct communication with one another throughpeer-to-peer communication 222, using the PIN-to-PIN protocol 82. Thus,the presence information, including the time zone information or timezone and location information, may be sent between the mobile devices10A and 10B through the peer-to-peer communication 222.

The presence information may also be transferred through a presenceinformation server or IM server 86. The IM server 86 may collect thepresence information from a number of mobile devices 10 and broadcastthe presence information to a number of other mobile devices 10. Forexample, if the user of mobile device 10A, hereinafter referred to asUser A, is a contact on mobile device 10B, then the IM server 86 willbroadcast the presence information of User A to mobile device 10B. TheIM server 86 may collect the presence information by polling the mobiledevices 10, or the mobile devices 10 may push the presence information,or both.

As will be discussed in further detail below, the time zone informationor time zone and location information may be transmitted between mobiledevices through other methods, in addition to presence information. Forexample, the time zone information may be sent as an instant message 84,68, or may be sent in the header of an instant message 84, 68.

Continuing with FIG. 5, once the time zone information, or time zone andlocation information, of mobile device 10A is received by mobile device10B, then the information is associated with User A and is updated onUser A's instant messaging profile 224 on mobile device 10B. Inparticular, the time zone information becomes part of User A's time zoneinformation 226.

Turning to FIG. 30, example computer executable instructions areprovided for providing time zone information as instant messagingpresence. At block 476, the mobile device 10 obtains time zoneinformation. As discussed above, the time zone information can beobtained using several different approaches (e.g. GPS, manual input,cell towers, etc.). At block 478, the mobile device 10 sends time zoneinformation through an instant messaging application 50 on the mobiledevice 10 to one or more other mobile devices 10. The other mobiledevices 10 correspond to one or more contacts associated with the mobiledevice's instant messaging application 50 to enable the other mobiledevices 10 to display the time zone information as presence.

In FIG. 31, example computer executable instructions are provided fordisplaying time zone information as instant messaging presence. At block480, a mobile device 10 receives time zone information from at least onecontact. The mobile device 10 then displays the time zone informationcorresponding to the at least one contact in one or more interfacesassociated with the contact (block 482). Examples of such interfaceswill be discussed further below.

Turning to FIG. 22, an embodiment of a time/date graphical userinterface (GUI) for interfacing with the time zone application 210 isprovided. The screen shot 402 of the GUI for the time or date, or both,shows displays the time zone field 404 and the current time zone status408. A time zone control 406 allows a user to adjust the time zonemanually. The time zone control 406 may be a drop down selection list,as shown here, a typed entry field, or any other input interface forentering or selecting a time zone. Some non-limiting examples of varioustime zones include: mid-Atlantic (−2); W. Central Africa (+1); Brussels(+1); Dublin, London (GMT); Nairobi (+3); Kuwait (+3); Pacific Time(−8); and Tijuana (−8).

Continuing with FIG. 22, in addition to providing the option to manuallyset the time zone, the screen shot 402 shows that there is a setting forautomatically updating the time zone 410. This automatic update setting410 may be enabled or disabled by the user by using a setting control412. The setting control 412 allows the user to turn on or off theautomatic update time zone feature, as well as to prompt the user that atime zone change will be made. The prompt, not shown, would let the userknow that a change in time zone has occurred and provide the user withthe option to change the time zone accordingly or, for example, maintainthe current time zone setting. As can be seen, the cursor or pointer422, as indicated by the shaded region, shows that the user is selectingthe “on” option, which enables the automatic updating of the time zone.

As discussed above, the time and time zone information may come from thecellular or network carrier 216 using a network time protocol. Thescreen shot 402 of the interface allows the user to select whether ornot the mobile device 10 uses the network time 414, as shown by thecorresponding network time controls 418, which provides a “yes” or “no”options. There is also a time format control 420 for setting the timeformat 416, for example, from either a twenty-four hour clock or atwelve hour clock.

Turning to FIG. 6, User A may adjust the instant messaging settings onmobile device 10A to display certain presence information. In the “MyProfile” screen shot 230, User A's display name 232 is provided, as wellas an icon or picture 234 associated with User A. The presence status236 may be changed from any one of the non-limiting examples: busy,available, do not disturb, away, or offline. The current status 238shows that User A is available. In one embodiment of the GUI, thedifferent presence status options may be selected from a drop down listas indicated by the downwards-facing arrow 240.

A PIN display 244 is also provided in the profile screen shot 230, whichshows User A's PIN 242.

The profile 230 also includes a time zone display 246 which shows thecurrent time zone 248. In the example screen shot 230, the time zone isEastern Time (ET), which is five hours behind Greenwich Mean Time (GMT).It can be appreciated that the format of the time zone information maybe displayed in any number of different ways, as desired by the user.Other time zone formats include GMT and Coordinated Universal Time(UTC). The profile 230 also provides an interface to allow a user toshow or share the time zone information, or time zone and locationinformation. The interface in FIG. 6 shows a selection box 250 forshowing time zone information only, and another selection box 252 forshowing time zone and location information. User A may select one of theboxes 250, 252 or none at all to indicate that time zone informationshould not be shared. Other GUIs that allow a user to select whether ornot time zone information, or time zone and location information, shouldbe shared with other mobile devices 10 are applicable to the principlesherein.

FIG. 7 shows a flow chart showing computer executable instructions of anIM application 50 when adjusting permissions with respect to whether ornot to share time zone, or time zone and location information, based onuser input. At block 254, the user adjusts the instant messagingsetting, for example for the user's own profile. At block 256, the userselects whether or not other instant messaging contacts are allowed toview their time zone information. If user indicates “no”, then, at block258, the user's IM application 50 does not send the time zoneinformation. If the user intends to allow others to view their time zoneinformation, then at block 260, the user also indicates whether or notto allow others to view the location information as well. If the userindicates “no”, then the IM application 50 sends only the time zoneinformation to the IM server 86 or the other mobile devices 10 as perblock 262. However, if the user indicates “yes”, then at block 264 theIM application 50 sends the time zone information and the locationinformation. It can be appreciated that, the principles described hereinwith respect to FIG. 7 may also be applied to send a mobile device'sroaming status or roaming information to the IM server 86 or the othermobile devices 10. Further details in this regard are discussed furtherbelow.

FIGS. 8 and 9 show screen shots of a user's contact list 266 and aprofile 278 of a contact on a user's contact list 277 having time zonepresence information associated with one or more contacts. Turning firstto FIG. 8, a user's contact list 266 shows a list of currentconversations 268 with contacts or buddies, as well a general list ofcontacts or buddies 276. In either one or both of the currentconversation list 268 and the general list 276, there is provided timezone information as presence information. For example, associated with acontact is a local time zone information in the form of current localtime. Although not shown, once a contact's time zone information isknown, the user's IM application 50 is able to calculate the currentlocal time of the contact by taking into account the user's local timeand the relative time difference between the user's time zone and thecontact's time zone. As shown in FIG. 8, the current local time 272 ofthe contact's are provided, and in some cases the location information274 as well. It can be appreciated the current local time 272 of acontact may be shown according to a twenty-four hour clock format, anA.M./P.M. format, or any other time format. The location information 274may be displayed as a country's flag, a name of a place, or any othertype of symbol.

Continuing with FIG. 8, it is shown in this example screen shot thatUser A is currently in conversations with the following contacts: UserB, User C, User D and User F. User B's local time is 9:00 PM and islocated in France. User C is in the same time zone as User A, and thus,the screen indicates that User C shares the same time zone as User A.User C does not show location information, as User C may have decided toonly share time zone information and not location information. User Dshows that the local time and location information is unavailable. Thus,it is possible that User D did not wish to share the time zone andlocation information. User F shows that the local time is 11:00 AM andthat User F is located in Canada.

In FIG. 9, if a contact's profile 278 is displayed in detail, forexample for User B's contact profile, then the display name 232 andpicture 234 are provided. The status bar 236, current status 238, PINdisplay 246 and the contact's PIN 242 are also displayed. The locationdisplay 280 shows that User B is located in France 282. The time zonedisplay 284 show the time zone information 282, which reads CentralEuropean Summer Time (CEST) 286, which is zero hours ahead or behindGMT. The current local time 288 is also displayed, in this case as 9:00PM 290. As discussed above, and as can be readily understood, thecurrent local time of a different time zone can be calculated based onthe relative time zone differences as well as the current time in atleast one of the time zones.

As discussed above, the time zone information may be transmitted througha peer-to-peer configuration or via an IM server 86. In one embodiment,a mobile device 10 may request another mobile device 10 for time zoneinformation. For example, in FIG. 10, mobile device 10A pings orrequests mobile device 10B for time zone and location information, asper block 292. Mobile device 10B receives the ping or request at block294. At block 296, the IM application 50 in mobile device 10B thendetermines whether others, or mobile device 10A in particular, is ableto view time zone information, or time zone and location information, orneither. This information is determined by the settings or permissionsof the instant messaging profile on mobile device 10B. If only time zoneinformation is shared, then at block 298, mobile device 10B sends thetime zone information to mobile device 10A, so that mobile device 10Amay then display mobile device 10B's time zone information. If both timezone and location information are shared, then at block 300, mobiledevice 10B sends the time zone and location information to mobile device10A, so that mobile device 10A can display the same at block 306. Ifneither information is available to be shared, then at block 302, mobiledevice 10B sends an “unavailable” response to mobile device 10A, sothat, at block 308, mobile device 10A accordingly displays that User B'stime zone presence information is unavailable.

Turning to FIGS. 11, 12 and 13, a number of screen shots are providedshowing a conversation between User A and User B on User A's mobiledevice 10A. Conversation window 310 shows that User A is engaged in aconversation with User B. A series of messages 312, 314, and 322 havebeen exchanged between User A and User B. A message box 316 allows UserA to compose messages to be sent to User B. In some cases, User A maywish to display when a message was sent or received. In one embodiment,when a cursor or pointer 326 is moved beside a certain message, or tohighlight a certain message, then the time and date the message was sentor received is displayed. In FIG. 11, the cursor or pointer 326 is movedbeside message 312 from User B. This causes the pop-up display 318 toappear, which shows when the message was received according to User A'slocal time (e.g. 3:00 PM), as well as according to User B's local time(e.g. 9:00 PM). Similarly, in FIG. 12, when the cursor or pointer 326 ismoved beside message 314 from User A, then the pop-up display 320appears to indicate when the message was sent according to User A'slocal time, as well as User B's local time. In FIG. 13, a similar pop-updisplay 324 is shown, which also includes the location of User B.

A process for utilizing the interface shown in FIGS. 11, 12 and 13 isprovided in FIG. 14, whereby at block 328 the cursor or pointer 326 ismoved over a sent or received message. At block 330, the user's IMapplication 50 determines whether it is aware of the contact's time zoneinformation. If not, then at block 332, the IM application 50 does notdisplay the contact's local time. If so, then at block 334, the IMapplication determines whether the contact's location information isavailable as well. If only the time zone information is available, thenat block 336, the user's IM application 50 will display the contact'slocal time that a message was sent 338 by the user, or when a messagewas received 340 by the user, for example, through the form of a pop-updisplay. If both the time zone and location information are available,then as per block 342, the contact's location 344 and the contact'slocal time that the message was sent 338, or when it was received 340will be displayed.

FIG. 15 shows another embodiment of how time zone information, or timezone and location information can be transferred between users. At block346, a mobile device 10 receives a new message from the user's contact.The IM application 50 determines if the new message includes thecontact's time zone information, as per block 348. If not, then at block350 the IM application 50 does not display the contact's local time. Ifso, the IM application 50 also determines if the new message alsoincludes location information, as per block 352. If only time zoneinformation is available, as per block 354, then the contact's time zoneinformation is displayed, for example, in any of one of the followingforms: current local time 356; local time message was sent 358; andlocal time message was received. If location information is available aswell, then in addition to displaying the contact's time zoneinformation, at block 362, the contact's location 364, is displayed.

Turning to FIGS. 16, 17 and 18, several screen shots are providedshowing a conversation window 310 between User A and User B on User A'smobile device 10A. In the embodiment shown here, the conversation window310 also displays the current local time of User B in the header portion368. In FIG. 16, messages 366 and 312 have been exchanged between User Aand User B. In the message box 316, User A is composing a new message370, as indicated by the cursor or pointer 326. Once User A selects“send” 380 or attempts to the send the new message 370, then a prompt372 is displayed, as per FIG. 17. The prompt 372 is related to the localtime of User B and thus warns or otherwise notifies User A of thedifference between its current time zone and that associated with UserB. In this example, User B's current local time is 12:00 AM and may besleeping. The prompt 372 confirms whether or not User A wishes to sendthe message now and provides option buttons 374, 376, and 378 toindicate the next step. In particular, there is a “yes” option 374, a“no” option 376, and a “yes: do not show this again” option 378. It canbe appreciated that such intelligent or rule-based prompts may beperceived as undesirable to certain users, and thus can be disabled, asper option button 378.

In this example, User A selects the “yes” option 382 and, in FIG. 18,the new message 370 is sent as indicated by message 314.

FIG. 19 shows the process of the interface illustrated in FIGS. 16, 17and 18. At block 384 a new instant message is composed in the user's IMapplication 50 and is to be sent to mobile device 10B. At block 386,before the user's IM application 50 sends the message, the IMapplication 50 retrieves or determines the current local time of mobiledevice 10B. Then a time period rule is applied in block 388, determiningwhether or not the current local time of mobile device 10B is betweentime X and time Y (e.g. between 10:00 PM and 7:00 AM). If the answer is“no”, then at block 390 the new message is sent to mobile device 10B. If“yes”, then a prompt 372 is displayed to User A, indicating that User Bmay be sleeping and to confirm if the new message should be sent, as perblock 392. Based on the decision on whether or not to send the newmessage now, as per block 394, if the answer is “yes”, then the newmessage is sent as per block 390. If not, the new message is not sentnow as per block 396.

It can be appreciated that any number of intelligent or rule-baseddecisions can be made based on the time zone information of a contact,as well the location. Other examples of intelligent or rule-baseddecisions relate to the time at which meetings or appointments arescheduled, and when a contact may be busy or available. For example, atime zone related rule specifies that work-related meetings may only bescheduled during work hours of the users or contacts participating inthe meeting, taking into account that the users or contacts may be indifferent time zones. Thus, if a user attempts to schedule a meetingwith a contact, whereby the meeting is outside the contact's businesshours, then the IM application 50 may prompt the user with a message.Such a message could read: “contact may not be available for aconference call/meeting since it is outside their core business hours”.The prompt may also suggest an alternate meeting time that suits thebusiness hours of both the user and the contact, taking into account thedifferent time zones.

Turning to FIG. 20, another embodiment of a user's contact list 266 isprovided, wherein the relative time difference 398 between a contact'stime zone and the user's time zone is also displayed. The relative timedifference 398 may be calculated or determined using a look-up chart ofdifferent time zones. It can be readily understood that displaying thetime difference 398 may assist allow the user to more easily discern thecurrent situation or presence of a contact.

Turning to FIG. 21, another embodiment of conversation window 310between User A and User B is provided, wherein a new message alert 400from an ancillary user shown. The new message alert 400 includes thecurrent local time of the ancillary user. For example, while User A andUser B are conversing, a new message alert 400 from User F appears,whereby the new message alert 400 show that User F's local time is 11:00AM.

Turning to FIG. 23, another embodiment of a user's contact list 266 isprovided. When a contact on the user's contact list 266 changes timezones, a notification is sent to the user's IM application 50 that thecontact has changed time zones. For example, a contact (e.g. User C andUser F) may have changed time zones, so that a notification 422, 424 isdisplayed on the contact list 266 beside the contact. A notification mayinclude a symbol or text, or both, and may read, for example, “*New timezone!”.

FIG. 24 shows another type of notification, which includes a message box426 that indicates to the user that a certain contact's time zone haschanged. If the certain contact's new time zone is the same as theuser's time zone, then the message box 426 may also display that thecontact's new time zone is the same as the user's time zone. It can beappreciated that any type of display or alert for notifying the userthat a contact's time zone has been updated is applicable to theprinciples described herein.

FIG. 25 shows an example method for providing notification that a timezone of a contact has been updated. User B may be a contact on User A'scontact list. User B's mobile device, mobile device B 10B, updates thetime zone information with a new time zone (block 430). The new timezone information can be updated automatically or manually. For example,when mobile device B 10B moves from one time zone to another time zone,mobile device B 10B may be able to detect the change in time zonethrough the communication subsystem 104 or the GPS receiver 121.Alternatively, User B may manually change the time zone setting onmobile device B 10B. Upon detecting and updating the new time zone,mobile device B sends the new time zone information to one or more othermobile devices or to the IM server 226 (block 432). User A's mobiledevice, mobile device A 10A, receives mobile device B's new time zoneinformation (block 434). Upon detecting a change in mobile device B'stime zone information, mobile device A 10A displays a notification thatUser B or mobile device B 10B has a new or different time zone (block436). Mobile device A 10A then determines whether or not mobile deviceB's new time zone is the same as mobile device A's current time zone(block 438). If so, at block 440, mobile device A 10A displays anotification that mobile device B's new time zone is the same as mobiledevice A's time zone. If not, at block 442, no action is taken.Alternatively, at block 442, the time difference between the two timezones is displayed.

Although not shown, it can also be appreciated that a user's mobiledevice 10 can be notified when a contact's previous time zone was thesame as the user's time zone, and then has been recently changed to adifferent time zone. Thus, the user is notified that the contact is nolonger shares the same time zone as the user.

By providing a notification that a contact has updated or changed theirtime zone, the user can keep better track of the presence or change inpresence of the contact. Such time zone presence, or change in time zonepresence, allows a user to better determine when to contact a user.

Turning to FIG. 26, another example embodiment of a “My Profile” screenshot 230 is provided, similar to the screen shot shown in FIG. 6. InFIG. 26, a roaming display 446 is shown on the screen shot 230. Anoption box 448 allows a user to control whether or not to provide theuser's roaming status or roaming information as part of the IM presenceinformation to the user's contacts. As discussed above, the roamingstatus or roaming information may be sent to the IM server 86 or one ormore other mobile devices 10 according to the principles described withrespect to FIG. 7.

The term “roaming” as used herein may refer to the ability for a user touse their mobile device 10 outside their regular phone or data servicearea. For example, when a user travels with their mobile device 10outside of the “home” service area defined by a phone or data serviceprovider, then the mobile device 10 is considered to be roaming. In somecases, higher cost rates may be charged for calls or data transmitted orreceived while roaming. It can be appreciated that the methods andsystems for detecting when a mobile device 10 is roaming is known to aperson skilled in the art. Such methods and systems for detectingroaming may include receiving a data message from the network carrier216 that the mobile device 10 is outside its regular phone or dataservice area.

Turning to FIG. 27, a contact list 266 provides a roaming statusindicator 450 associated with one or more of the contacts on the contactlist 266. The roaming status indicator 450 shows the user that acontact's mobile device 10 is currently roaming. Thus, the user candetect whether or not the contact is within or away from their regularservice provider area. The combination of showing both the time zoneinformation and roaming status indicator 450 allows the user todetermine whether a contact is likely to be in a time zone that isdifferent from their regular time zone. For example, when a contact isin their regular time zone, they are likely to be in the area of theirregular service provider. However, if the contact travels to a differentlocation outside the coverage area of their regular service provider,then the roaming status indicator 450 is displayed alongside thecontact's time zone information. The user can then determine that thereis a possibility that the contact's time zone is not their regular timezone, since they are currently roaming.

In another embodiment (not shown) a user can also choose whether or notto display their regular time zone information as IM presenceinformation through the IM application 50. The term “regular time zone”as used herein may refer to the time zone in which a user spends themajority of their time. A GUI, similar to the “My Profile” screen 230 inFIG. 26, may include an option to enable the display of their regulartime zone information. On the contact list 266, an IM application 50 maycompare a contact's regular time zone information and the contact'scurrent time zone information. If the contact's regular time zoneinformation and their current time zone information do not match, thenan indicator is shown to indicate the difference between the contact'scurrent time zone and the contact's regular time zone. Such an indicatorof the contact's presence allows the user to determine that the contactis in a time zone that is different from their regular time zone.

Turning to FIG. 28, a set of example computer executable instructions isprovided for determining when time zone information is broadcasted orretrieved, or both. In some circumstances, the mobile device 10 or thecommunication subsystem 104 may be turned off. For example, a user maydeactivate the communication subsystem 104 or turn off the mobile device10 when travelling on an airplane, or to conserve power. It can beappreciated that when either the communication subsystem 104 or themobile device 10 are deactivated, a user cannot broadcast their timezone information as IM presence or receive time zone information fromtheir contacts. During this period of deactivation, a user's time zonemay have changed, or one or more of the contacts' time zones may havechanged. Therefore, at block 456, the IM application 50 detects that thecommunication subsystem 104 has been reactivated or that the mobiledevice 10 has been reactivated. At block 458, the mobile application 50determines the current time zone information and, at block 460,broadcasts the current time zone information to one or more of thecontacts (e.g. the contacts' mobile devices 10). At block 462, themobile application 50 retrieves time zone information from the contactsand updates the contact list. In this way, when the communicationsubsystem 104 or the mobile device 10 are reactivated, the time zoneinformation is updated on the IM application and exchanged between theuser and the contacts.

FIG. 29 shows another example embodiment of a location-based contactlist 466, with similar functionality to the contact lists 266 describedabove. However, in FIG. 29, a map 468 of the world is provided toillustrate the different time zones. Contacts 472 are organized orgrouped on the contact list 466 according to their time zones. Forexample, contacts belonging to a first time zone form a first group,while contacts belonging to a second time zone form a second group. Inthis way the user can more easily determine the time zone information ofthe contacts, as well as to determine which contacts share common timezones. In the embodiment shown in FIG. 29, the groups of contacts arepositioned to correspond with the location of the time zones on the map468. For example, User A's current time zone shares the same time zonewith User B and User D, and the position of their contacts 472 on thecontact list 466 corresponds with the time zone for New York city,U.S.A. as shown on the map 468. User C is in a different time and theposition of their contact 472 on the contact list 466 corresponds withthe time zone for Vancouver, Canada as shown on the map 468. There maybe a time indicator 470 associated with each grouping of one or morecontacts 472. The time indicator 470 may show the current time or thenumber of hours ahead or behind the user's time. The time indicator 470in FIG. 29 shows the time difference between a contact and the user. Forexample, the time in Vancouver is 3 hours behind the time in New Yorkcity. Through the contact list 466, a user can provide a selection inputassociated with a contact to, for example, invoke a conversation window310 with the selected contact.

It can be appreciated that other displays of a contact list 466 showingcontacts grouped by time zone are applicable to the principles describedherein. It can be further appreciated that, where location informationof a contact is provided, the contacts can be positioned on a map 468according to their location.

The steps or operations in the flow charts described herein are just forexample. There may be many variations to these steps or operationswithout departing from the spirit of the invention. For instance, thesteps may be performed in a differing order, or steps may be added,deleted, or modified.

It can also be appreciated that the displays or screens described hereinare just for example. There may be many variations to the configurationand arrangement of information and user interface controls withoutdeparting from the scope of the above principles. For instance, theinformation and the user interface controls may be in a differing order,or may be added, deleted, or modified.

Although the above has been described with reference to certain specificembodiments, various modifications thereof will be apparent to thoseskilled in the art without departing from the scope of the claimsappended hereto.

The invention claimed is:
 1. A method of displaying time zoneinformation for at least one contact listed in an instant messagingapplication on a mobile device, said method comprising said mobiledevice: receiving said time zone information for said at least onecontact; determining that said time zone information for said at leastone contact has changed; and displaying new time zone information forsaid at least one contact in one or more interfaces associated with saidinstant messaging application.
 2. The method according to claim 1,further comprising displaying a first notification of said new time zoneinformation.
 3. The method according to claim 1, wherein said one ormore interfaces comprises any one or more of a contact list comprisingsaid at least one contact, and a respective conversation with said atleast one contact.
 4. The method according to claim 3, furthercomprising displaying an indicator that said at least one contact andsaid mobile device share said time zone information if it is determinedthat said time zone information corresponding to said at least onecontact is the same as time zone information for the mobile device. 5.The method according to claim 3, wherein said time zone information isdisplayed in said conversation, the method further comprising displayinga local time of when a message was sent or received in said conversationaccording to said time zone information of said at least one contact. 6.The method according to claim 3, wherein said time zone information isdisplayed in said conversation, the method further comprising: detectingcomposition of a new message to said at least one contact; anddisplaying a prompt to confirm whether or not to send said new messageprior to sending said new message to said at least one contact afterdetermining that a current local time of said at least one contact iswithin a specified time period.
 7. The method according to claim 3,wherein said time zone information is displayed in said contact list,said contact list comprising a plurality of contacts, said mobile devicereceiving and displaying time zone information corresponding to each oneof said plurality of contacts.
 8. The method according to claim 7,wherein a first one or more of said plurality of contacts associatedwith a first time zone form a first group in said contact list, and,optionally, a second one or more of said plurality of contactsassociated with a second time zone form a second group in said contactlist.
 9. The method according to claim 3, wherein said time zoneinformation is displayed in said contact list, said contact listcomprising a map showing locations of different time zones, said atleast one contact being positioned to correspond to a location of saidtime zone information on said map.
 10. The method according to claim 3,further comprising: displaying a second notification that said time zoneinformation for said at least one contact is now the same as said timezone information of said mobile device if it is determined that said newtime zone information is the same as time zone information of saidmobile device; and displaying a time difference between said new timezone information and said time zone information of said mobile device ifit is determined that said new time zone information is not the same astime zone information of said mobile device.
 11. The method according toclaim 3, further comprising displaying an indicator that said at leastone contact no longer shares the same time zone as said mobile device ifsaid time zone information was the same as time zone information of saidmobile device and if said new time zone information is different fromsaid time zone information of said mobile device.
 12. The methodaccording to claim 1, further comprising displaying a roaming indicatorwith said new time zone information if said at least one contact islocated outside a coverage area for a regular phone or data serviceprovider of said at least one contact.
 13. The method according to claim1, further comprising: comparing regular time zone information of saidat least one contact and said new time zone information; and displayingan indication that said regular time zone information for said at leastone contact and said new time zone information are different if saidregular time zone information and said new time zone information do notmatch.
 14. A mobile device comprising: a processor; and at least onememory, the at least one memory storing instructions executable by theprocessor to: receive said time zone information for said at least onecontact; determine that said time zone information for said at least onecontact has changed; and display new time zone information for said atleast one contact in one or more interfaces associated with said instantmessaging application.
 15. The mobile device according to claim 14,further comprising instructions executable by the processor to display afirst notification of said new time zone information.
 16. The mobiledevice according to claim 14, wherein said one or more interfacescomprises any one or more of a contact list comprising said at least onecontact, and a respective conversation with said at least one contact.17. The mobile device according to claim 16, further comprisinginstructions executable by the processor to display an indicator thatsaid at least one contact and said mobile device share said time zoneinformation if it is determined that said time zone informationcorresponding to said at least one contact is the same as time zoneinformation for the mobile device.
 18. The mobile device according toclaim 16, wherein said time zone information is displayed in saidconversation, the computer executable instructions further comprisinginstructions executable by the processor to display a local time of whena message was sent or received in said conversation according to saidtime zone information of said at least one contact.
 19. The mobiledevice according to claim 16, wherein said time zone information isdisplayed in said conversation, the computer executable instructionsfurther comprising instructions executable by the processor to: detectcomposition of a new message to said at least one contact; and display aprompt to confirm whether or not to send said new message prior tosending said new message to said at least one contact after determiningthat a current local time of said at least one contact is within aspecified time period.
 20. The mobile device according to claim 16,wherein said time zone information is displayed in said contact list,said contact list comprising a plurality of contacts, said mobile devicereceiving and displaying time zone information corresponding to each oneof said plurality of contacts.
 21. The mobile device according to claim20, wherein a first one or more of said plurality of contacts associatedwith a first time zone form a first group in said contact list, and,optionally, a second one or more of said plurality of contactsassociated with a second time zone form a second group in said contactlist.
 22. The mobile device according to claim 16, wherein said timezone information is displayed in said contact list, said contact listcomprising a map showing locations of different time zones, said atleast one contact being positioned to correspond to a location of saidtime zone information on said map.
 23. The mobile device according toclaim 16, further comprising instructions executable by the processorto: display a second notification that said time zone information forsaid at least one contact is now the same as said time zone informationof said mobile device if it is determined that said new time zoneinformation is the same as time zone information of said mobile device;and display a time difference between said new time zone information andsaid time zone information of said mobile device if it is determinedthat said new time zone information is not the same as time zoneinformation of said mobile device.
 24. The mobile device according toclaim 16, further comprising instructions executable by the processor todisplay an indicator that said at least one contact no longer shares thesame time zone as said mobile device if said time zone information wasthe same as time zone information of said mobile device and if said newtime zone information is different from said time zone information ofsaid mobile device.
 25. The mobile device according to claim 14, furthercomprising instructions executable by the processor to display a roamingindicator with said new time zone information if said at least onecontact is located outside a coverage area for a regular phone or dataservice provider of said at least one contact.
 26. The mobile deviceaccording to claim 14, further comprising instructions executable by theprocessor to: compare regular time zone information of said at least onecontact and said new time zone information; and display an indicationthat said regular time zone information for said at least one contactand said new time zone information are different if said regular timezone information and said new time zone information do not match.
 27. Anon-transitory computer readable medium comprising computer executableinstructions for displaying time zone information for at least onecontact listed in an instant messaging application on a mobile device,said computer executable instructions comprising instructions for:receiving said time zone information for said at least one contact;determining that said time zone information for said at least onecontact has changed; and displaying new time zone information for saidat least one contact in one or more interfaces associated with saidinstant messaging application.